Gateway backup system and method

ABSTRACT

In embodiments, a system and method backs up and restores data stored on a gateway using a signature having sub-signatures that represent specific categories of data elements of the data, the categories regarding the operation of one or more actuating devices and possibly other items, the system and method changing the operation of the one or more actuating devices and possibly the other items based on restored or updated data elements of the data stored on the gateway.

BACKGROUND Field of the Disclosure

The present disclosure relates to a backup system and method, and moreparticularly to a backup system and method that includes categorizedelements of data and corresponding signatures to improve backup andrestore efficiency of a gateway and networked devices, such as actuatingdevices.

Brief Description of Related Art

Gateways may store data used to communicate with other electronicdevices over a network. That data may be updated or become corrupted.Therefore, the data may be periodically backed up so that it can berestored when desired. Such a backup system may use significantresources, including bandwidth, to keep the data stored on the gatewayerror-free and up-to-date.

There may therefore be a need for a backup system and method thatefficiently backs up and restores data on a gateway. There may also be aneed for a backup system and method that efficiently backs up andrestores such data to thereby facilitate the accurate communication ofthe gateway with electronic devices. There may also be a need for abackup system and method that efficiently backs up and restores data ona gateway to thereby facilitate the change of operation, by way of thegateway, of those electronic devices.

SUMMARY OF THE INVENTION

In one embodiment, a backup method includes: storing, on a gateway on alocal area network, data that comprises data elements that are each in adifferent one of a plurality of categories that together regardoperation of a plurality of actuating devices on the local area network;storing the data on a database; creating a signature comprisingsub-signatures that each represent a different one of the data elementsalong with the category that data element is in; updating the datastored on the gateway by updating the data elements, such that theupdated data elements of the updated data comprise the data elementsexcept that one or more of the data elements in one or more of theplurality of categories are changed; creating an updated signature thatcomprises updated sub-signatures that each represent a different one ofthe updated data elements of the updated data stored on the gateway, andthus each represent said different one of the plurality of categories;determining that the updated signature does not match the signature;determining, for each of the categories, whether the updatedsub-signature and sub-signature representing that category aredifferent; and copying, from the gateway to the database, for eachcategory in which the updated sub-signature and sub-signaturerepresenting that category are different, the updated data element inthat category and thereby replacing, with that updated data element, thedata element in that category stored on the database.

In another embodiment, a backup system includes a gateway on a localarea network, the gateway comprising a processor and a computer readablestorage medium, the computer readable storage medium including codeexecutable by the processor to: store, on a gateway on a local areanetwork, data that comprises data elements that are each in a differentone of a plurality of categories that together regard operation of aplurality of actuating devices on the local area network; store the dataon a database; create a signature comprising sub-signatures that eachrepresent a different one of the data elements along with the categorythat data element is in; update the data stored on the gateway byupdating the data elements, such that the updated data elements of theupdated data comprise the data elements except that one or more of thedata elements in one or more of the plurality of categories are changed;create an updated signature that comprises updated sub-signatures thateach represent a different one of the updated data elements of theupdated data stored on the gateway, and thus each represent saiddifferent one of the plurality of categories; determine that the updatedsignature does not match the signature; determine, for each of thecategories, whether the updated sub-signature and sub-signaturerepresenting that category are different; and copy, from the gateway tothe database, for each category in which the updated sub-signature andsub-signature representing that category are different, the updated dataelement in that category and thereby replace, with that updated dataelement, the data element in that category stored on the database.

In yet another embodiment, a data backup system includes: a remotedatabase that is remote from a local area network, the remote databasestoring: first data that comprises first data elements that are each ina different one of a plurality of categories regarding the operation ofa plurality of actuating devices on the local area network; and a firstsignature comprising first sub-signatures that each represent adifferent one of the data elements along with the correspondingdifferent one of the plurality of categories that data elements is in.The data backup system in that embodiment may also include a gateway onthe local area network, the gateway storing: second data that comprisessecond data elements that each are in a different one of the pluralityof categories regarding the operation of the plurality of actuatingdevices on the local area network; and a second signature that comprisessecond sub-signatures that each represent a different one of the seconddata elements of the second data, and thus each represent said differentone of the plurality of categories that second data element is in,wherein the gateway includes a processor and a computer readable storagemedium including code executable by the processor to: determine whetherthe second signature matches the first signature, and if the secondsignature does not match the first signature, determine, for each of theplurality of categories, whether the corresponding second sub-signatureand first sub-signature representing that category are different; andcopy, from the gateway to the remote database, for each category inwhich the second sub-signature and first sub-signature representing thatcategory are different, the second data element in that category andthereby replacing, with that second data element, the first data elementin that category stored on the remote database.

In another embodiment a data backup system includes; a remote databasethat is remote from a local area network, the remote database storing aplurality of sets each of both first data and a corresponding firstsignature, wherein the first data is different in at least a pluralityof the sets and the first signature is different in at least a pluralityof the sets, wherein for each of the sets: the first data comprisesfirst data elements that each represent a different one of a pluralityof categories regarding operation of a plurality of actuating devices onthe local area network; and the first signature comprises firstsub-signatures that each represent both a different one of the firstdata elements of the first data and the category that different one ofthe first data elements is in. The data backup system in that embodimentmay also include a gateway on the local area network, the gatewaystoring: second data that comprises second data elements that each arein said different one of the plurality of categories regarding theoperation of the plurality of actuating devices on the local areanetwork; and a second signature that comprises second sub-signaturesthat each represent a different one of the second data elements of thesecond data, and thus each represent said different one of the pluralityof categories that second data element is in, wherein the gatewayincludes a processor and a computer readable storage medium includingcode executable by the processor to: determine, for a selected one ofthe sets of both first data and corresponding first signature, whetherthe first signature matches the second signature, and if the firstsignature does not match the second signature, determine, for each ofthe plurality of categories, whether the first sub-signature and secondsub-signature representing that category are different; and copy fromthe remote database to the gateway, for the selected one of the sets offirst data and corresponding first signature, for each firstsub-signature that is different than the corresponding secondsub-signature for each of the represented plurality of categories, thefirst data element in that category and thereby replace, with that firstdata element, the second data element in that category stored on thegateway.

Other embodiments, which may include one or more parts of theaforementioned systems and methods or other parts, are alsocontemplated, and may thus have a broader or otherwise different scopethan the aforementioned systems and methods. Thus, the embodiments inthis Summary of the Invention are mere examples, and are not intended tolimit or define the scope of the invention or claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For the present disclosure to be easily understood and readilypracticed, the present disclosure will now be described for purposes ofillustration and not limitation, in connection with the followingfigures.

The accompanying drawings, wherein like reference numerals are employedto designate like components, are included to provide a furtherunderstanding of the present inventions, are incorporated in andconstitute a part of this specification, and show embodiments of thosesystems and methods that together with the description serve to explainthose systems and methods.

Various other objects, features and advantages of the invention will bereadily apparent according to the following description exemplified bythe drawings, which are shown by way of example only, wherein:

FIG. 1 illustrates an embodiment of a backup system for a gateway;

FIG. 2 illustrates an embodiment of a gateway that may be included inthe backup system;

FIG. 3 illustrates an embodiment of a local area network the backupsystem for the gateway may operate with or include at least in part;

FIG. 4 illustrates embodiments of data and an associated signature usedin the backup system for the gateway;

FIG. 5 is a flow chart of embodiments of a method for backing up data ona gateway; and

FIG. 6 is a flow chart of embodiments of a method for restoring data ona gateway.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made to embodiments of gateway backup systems andmethods, examples of which are illustrated in the accompanying drawings.Details, features, and advantages gateway backup systems and methodstherefore will become further apparent in the following detaileddescription of embodiments thereof. The gateway backup systems andmethods provide for the efficient backup and restoration data stored onthe gateway. The gateway may use that data to, for example, controlnetworked devices in specified zones, such as the lighting in a specificarea of a building.

It is to be understood that the specific systems and methods describedin the following specification are simply exemplary embodiments of thepresent invention and are not to be considered as limiting.

Any reference in the specification to “one embodiment,” “a certainembodiment,” or a similar reference to an embodiment is intended toindicate that a particular feature, structure or characteristicdescribed in connection with the embodiment is included in at least oneembodiment of the invention. The appearances of such terms in variousplaces in the specification do not necessarily all refer to the sameembodiment. References to “or” are furthermore intended as inclusive, so“or” may indicate one or another of the ored terms or more than one oredterm.

FIG. 1 illustrates an embodiment of a backup system 1 for a gateway. Thebackup system 1 may backup and restore data on the gateway 10. Thebackup system 1 may include the gateway 10 and a database 100.

The gateway 10 may be in communication with the database 100 as desired.For example, in an embodiment, the database 100 is a remote database ona remote network 110, which may be a network remote from a local areanetwork on which the gateway 10 resides and accessible via the Internet.The network 110, if remote, may be considered one or more networksremote from the local area network, and may be part of a cloud. Such adatabase 100 may be on or in communication with, such as through theInternet, a remote server 120, which may be a server on the remotenetwork 110. The gateway 10 may be in communication with the database100, if remote, via another gateway 11, which may communicate with thedatabase 100 via the remote server 120. In another embodiment, thegateway 10 communicates with the database 100 via the remote server 110directly, without the gateway 11. In another embodiment, the gateway 11may instead be a router. In an embodiment, the database 100 may beconsidered one or more databases that together stored the various dataand signatures described herein.

The gateway 10 in the system 1 may control one or more networkeddevices, such as one or more actuating devices 74 over a local areanetwork such as within a building, such as described herein. In anembodiment, the system 1 may also include or operate with one or moresensing devices 75 that sense conditions that trigger certain actionswith respect to one or more of the actuating devices 74, such as by wayof the gateway 10 sending signals directly or indirectly to thoseactuating devices 74 to so act when those sensed conditions are met. Inembodiments, the one or more actuating devices 74 and one or moresensing devices 75 may be on the local area network, and thus incommunication over the local area network directly or indirectly withthe gateway 10.

The actuating devices 74 may be, for example, lighting fixtures or otherlighting, blinds, HVAC systems and devices, and/or various other powereddevices, and/or manually or otherwise operated switches or othercontrollers for the aforementioned or other powered devices. In anembodiment, one or more of the actuating devices 74 include both thepowered devices (e.g., lighting fixtures) and their switches or othercontrollers. As described herein, operation (or change in operation) ofan actuating device 74 that is a switch for a light or lights mayoperate (or change the operation of) the light or lights in a specifiedway.

The sensing devices 75 may be, for example, light level sensors,temperature sensors, motion sensors, and/or other ambient or othercondition sensors or detectors. In an embodiment, one or more of thesensing devices 75 may be included in one or more powered devices, suchas one or more powered devices described in the paragraph above.

In one embodiment as shown in FIG. 1, the local area network may includethereon the gateway 10 along with the gateway 11, and one or moreactuating devices 74 and one or more sensing devices 75. The gateway 10may also be in communication with a general purpose computer 76, whichmay also be a part of the system 1 and local area network. In anembodiment, a user may use the general purpose computer 76 to prompt thegateway 10 to, such as described herein, back up or restore data. In anembodiment, the local area network includes the local area network 70 ofFIG. 3 described below or components thereof, and may be or include amesh network.

FIG. 2 illustrates an embodiment of the gateway 10. The gateway 10 maybe a network node that enables communication with other electronicdevices, such as one or more other gateways or routers and one or moreactuating and sensing devices, and may possibly communicate with one ormore other networks via the Internet. In an embodiment, the gateway 10controls the operation of one or more actuating devices 74, possiblybased, at least in part, on conditions one or more sensing devices 75sense. The gateway 10 may so control that operation by communicatingdirectly with, or indirectly with such as through other gateways orrouters, the actuating devices 74, and possibly also the sensing devices75 to signal to the actuating devices 74 to operate in specific waysand/or at specific times.

The gateway 10 may include a processor 12 and a wireless networkcommunication device 14. The processor 12 and wireless communicationdevice 14 may be combined in a controller 16, which may be amicrocontroller. The gateway 10 may include storage thereon, which maybe storage in the local area network for the gateway 10. The storage maybe memory 20, a data storage device 36, a combination of both memory andthe data storage device 36, or another device or devices for localstorage of data. Thus, the storage may be considered storage on thegateway 10 whether the data is stored directly on the gateway or on adevice or devices accessible by the gateway 10 over a local area networksuch as network 70 of FIG. 3. In an embodiment, the storage of thegateway may be or include a computer readable storage medium includingcode executable by the processor 12 of the gateway 10 to, at least inpart, operate the backup system 1 and backup methods for the gateway 10provided herein. The gateway 10 may also include a communication adaptor18, a communication adaptor port or connector 22, one or more inputdevices 24, diagnostic output devices 26, and a clock 38.

The wireless communication device 14 may be a radio board or module,such as, for example, a ZigBee® network communication device. Thegateway 10 may use the wireless communication device 14 to facilitatecommunications across one or more networks, including a wireless network40 and a wired network 42, one or both of which may be part of a localarea network (e.g. 70 shown in FIG. 3 and described below) and/or maycommunicate with one or more other networks.

It should be recognized that the gateway 10 may have fewer components ormore components than shown in FIG. 2. For example, if an input device 24or output device 26 is not desired, such a device may not be included inthe gateway 10.

The elements, including the processor 12, communication adaptor 18,memory 20, input device 24, output device 26, and data storage device 36related to the gateway 10 may communicate by way of one or morecommunication busses 30. Those busses 30 may include, for example, asystem bus or a peripheral component interface bus.

The memory 20 may, for example, include random-access memory (RAM),flash RAM, dynamic RAM, or read only memory (ROM) (e.g., programmableROM, erasable programmable ROM, or electronically erasable programmableROM) and may store computer program instructions and information. Thememory 20 may furthermore be partitioned into sections including anoperating system partition 32 where system operating instructions arestored, and a data partition 39 in which data is stored.

The processor 12 may be any desired processor and may be a part of acontroller 16, such as a microcontroller, may be part of or incorporatedinto another device, or may be a separate device. The processor 12 may,for example, be an Intel® manufactured processor or another processormanufactured by, for example, AMD®, DEC®, or Oracle®. The processor 12may furthermore execute the program instructions and process the datastored in the memory 20. In one embodiment, the instructions are storedin the memory 20 in a compressed or encrypted format. As used herein thephrase, “executed by a processor,” is intended to encompass instructionsstored in a compressed or encrypted format, as well as instructions thatmay be compiled or installed by an installer before being executed bythe processor 12.

The data storage device 36 may be, for example, non-volatile batterybacked static random-access memory (RAM), a magnetic disk (e.g., harddrive), optical disk (e.g., CD-ROM) or any other device or signal thatcan store digital information. The data storage device 36 mayfurthermore have an associated real-time clock 38, which may beassociated with the data storage device 36 directly or through theprocessor 12 or controller 16. The real-time clock 38 may trigger datafrom the data storage device 36 to be sent to the processor 12, forexample, when the processor 12 polls the data storage device 36. Datafrom the data storage device 36 that is to be sent across the network 40or 42 through the processor 12 may be sent in the form of messages inpackets if desired. Those messages may furthermore be queued in or bythe processor 12.

The communication adaptor 18 permits communication between the gateway10 and other gateways 11 (depicted in FIG. 3), node 72 (depicted in FIG.3) such as a router or gateway, devices, or other nodes coupled to thecommunication adaptor 18 at the communication adaptor connector 22. Thecommunication adaptor 18 may be a network interface that transfersinformation from a node such as a node 72 that is a router or gateway, anetworked device such as an actuating device 74 or sensing device 75(depicted in FIGS. 1 and 3), a general purpose computer 76 (depicted inFIGS. 1 and 3), a user interface 77 such as a cell phone or part thereof(depicted in FIG. 3) or another gateway 11 to the gateway 10 or from thegateway 10 to a node 11, 72, 74, 75, 76, or 77. The communicationadaptor 18 may be an Ethernet adaptor or another adaptor for anothertype of network communication. It will be recognized that the gateway 10may alternately or in addition be coupled directly to one or more otherdevices through one or more input/output adaptors (not shown).

The input device 24 and output device 26 may couple the gateway 10 toone or more input or output devices such as, for example, one or morepushbuttons and diagnostic lights or displays. It will be recognized,however, that the gateway 10 does not necessarily need to have an inputdevice 24 or an output device 26 to operate. Moreover, the data storagedevice 36 may also not be necessary for operation of the gateway 10 asdata may be stored in memory 20, for example, or otherwise stored on thelocal area network (e.g., 70 of FIG. 3) as described herein such thatthis local data storage is considered part of the gateway 10 asconnected thereto.

The processor 12 may include or be attached to the real-time clock 38such that the real-time clock 38 may prompt the processor 12 to read orretrieve data regarding scheduled events when or subsequent to whenthose scheduled events are to occur. For example, the real-time clock 38may indicate that it is time for one or more actuating devices 74 (andpossibly one or more sensing devices 75 in an embodiment) to operate ina certain way. The data may be read or retrieved by the gateway 10 fromlocal storage, such as the data storage device 36 or memory 20 or otherlocal storage as described above. The retrieved data regarding thescheduled event or events, or a signal related to that data, may then betransmitted across the network 40 or 42, such as to the one or moreactuating devices 74, possibly through other nodes, to signal for thosedevices 74 to so operate. One or more of such scheduled events maytrigger messages to be sent at a time or in a cycle and, where more thanone message is triggered to be sent across the network 40 or 42, thosemessages may form a queue. The queue may be created at themicroprocessor 16.

Other devices, such as those illustrated in FIG. 1 and/or FIG. 3,including nodes 72 such as routers or gateways, actuating devices 74,sensing devices 75, the general purpose computer 76, FIGS. 1 and 3), andthe user interface 77 may alternately be configured with some or all ofthe components discussed in connection with FIG. 2.

FIG. 3 illustrates an embodiment of a local area network 70, which maybe or include a mesh network, for example, and which backup system 1 mayoperate with or include at least in part. Thus, the local area network70 may include the gateway 10, and may also include one or any desirednumber of additional gateways 11, one or more nodes 72 such as routersor gateways, a plurality of actuating devices 74 and sensing devices 75,and one or more general purpose computers 76 and cell phones or otheruser interfaces 77. The one or more gateways 11 may be configured likethe gateway 10 illustrated in FIG. 3, or may be of variousconfigurations.

The gateway 10 may transmit messages across the wireless network 40,wired network 42, or local area network 70 (of which networks 40 and 42may be a part). Those messages may enter a queue. The queue may be apacket queue where packets making up a message are queued fortransmission across one or more of the wireless network 40, wirednetwork 42, and local area network 70. The processor 12 of the gateway10 may place the packets in that queue.

The messages the gateway 10 transmits across the wireless network 40,wired network 42, and/or local area network 70 may include messages tobe used by one or more of the receiving nodes, e.g., one or more nodes72 such as routers or gateways, actuating devices 74, and/or sensingdevices 75 to cause an event with respect to one or more of theactuating devices 74, such as operating a switch to thereby turn a lighton or off or energize a motor on a motorized window shade or blind.

In an embodiment of the backup system 1 for a gateway, data is stored onthe gateway 10, which, as described above, may mean the data is storedin the memory 20, a data storage device 36, a combination of both memory20 and the data storage device 36, or another device or devices forlocal storage of data on the local area network 70. The data stored onthe gateway 10 may include a plurality of data elements that are each ina different one of a plurality of categories.

FIG. 4 illustrates embodiments of such data 200 that may be stored onthe gateway 10 of the system 1, and at least part of the data 200 ofwhich may regard operating a plurality of actuating devices 74 by way ofthe gateway 10. FIG. 4 also illustrates embodiments of a signature 400associated with the data 200, and which is addressed below. The data 200may be apportioned into data elements. The data elements may be portionsof a large dataset in RAM, functionally independent data blocks, or acombination of the two, for example.

In an embodiment, the gateway 10 stores on the gateway 10 the data 200including data elements in a plurality of categories that togetherregard the operation of a plurality of actuating devices 74 on a localarea network, such as the local area network 70 shown and described withrespect to FIG. 3. The categories so regard the operation of a pluralityof actuating devices 74 by together being used by the gateway 10 and/oranother component of the system 1 to trigger the operation in aspecified way of those devices 74. In an embodiment, those categoriesmay regard the operation of a plurality of actuating devices 74 at leastin some cases based, at least in part, on conditions sensed by one ormore sensing devices 75, such as for actuating devices 74 that are HVACsystems coupled with sensing devices 75 that are temperature sensors.Those categories may include, in an embodiment, a category of dataelement 210 that includes actuating device information, a category ofdata element 220 that includes scheduled events regarding the actuatingdevices, a category of data element 230 that includes zones in which theactuating devices are located, and a category of data element 240 thatregards groups of actuating devices. In an embodiment, one or more ofthe data elements 210-240 include information regarding the sensingdevices 75 and/or conditions the sensing devices 75 may sense thattrigger at least some of the operations of one or more of the actuatingdevices 74.

The category of the data 200 data element 210 that includes actuatingdevice information may include data that, at least in part, identifiesthe actuating devices 74 on the local area network (e.g. 70 of FIG. 3)on which the system 1 and its gateway 10 reside. The information mayregard one or more of user specified name, manufacturer, model, serialnumber, software version, type of device, and device capabilities ofeach actuating device 74 on the local area network. The information mayalso include user specified names of the devices 74. The information mayfurther include group membership assignments, which may assign thedevices 74 into various groups such as zoned-based groups, smart groups,and/or user-specified groups such as described below. In an embodiment,if one or more of the actuating devices 74 are switches or controllers,the aforementioned identification may identify the powered devices towhich those actuating devices 74 include or control. In an embodiment,the data element 210 may also include any of the aforementionedinformation but for one or more sensing devices 75.

The category of the data 200 data element 220 that includes scheduledevents regarding the actuating devices may regard rules and schedules ofoperation of the actuating devices 74. The rules may be configurablebehavior of the devices 74 based on sensor states, such as specifiedconditions to be sensed by one or more sensing devices 75, or timedevents. For example, the behavior may be the turning on or off atcertain times of certain fixtures or equipment that are, or arecontrolled by, actuating devices 74, the changing of color or intensityof lighting or equipment that are, or are controlled by, actuatingdevices 74, and the changing of temperature in a room by operation ofactuating devices 74 that are, or control, HVAC devices or systems atcertain times or based on temperatures detected by sensing devices 75that are temperature sensors, etc. The schedules of operation may regardthe times in which one or more devices 74 function according to therules of behavior. In an embodiment, the schedules of operation regard,in part, user-specified holidays that govern rules of behavior of thedevices 74 during those holidays. In an embodiment, the backup system 1may use the clock 38 of the gateway 10 to signal to the gateway 10 thearrival of the times when the devices 74 should function as specified bythe rules. In an embodiment, the data element 220 may also regardscheduled events, such as rules and schedules of operation, of thesensing devices 75.

The category of the data 200 data element 230 that includes zones inwhich the actuating devices 74 are located may include zones, such asareas or locations of a building where devices 74 on the local areanetwork (e.g., 70 in FIG. 3) reside. In an embodiment, the zones arewhere actuating devices 74 that are powered devices, or where thepowered devices associated with actuating devices 74 that are switchesor controllers, reside. The zones may include one or more of a listingof user-specified zones, zone occupancy and/or vacancy control options,ambient light sensing control options, and sub-zone configurations.User-specified zones may be areas or locations in a building specifiedby a user who communicates with the gateway 10 of the backup system 1.Such areas or locations may include, for example, conference rooms,floors, and wings of the building. Zone occupancy and/or vacancy controloptions may set parameters for operating the actuating devices 74, suchas lights and HVAC systems, when sensing devices 75, such as occupancysensors, detect the presence (or lack thereof) of people within thezones. Ambient light sensing control options may regard parameters forcontrolling light in various zones, such as areas of a building, thatreceive sunlight. The ambient light sensing control options may be tiedto sensing devices 75 that are light sensors in an embodiment. In anembodiment, ambient light sensing control options may be in the data 200data element 220 that includes scheduled events regarding actuatingdevices. The sub-zone configurations may regard areas within zones, suchas rooms within a floor. In an embodiment, the data element 230 thatincludes zones in which the actuating devices 74 are located may includescenes, which may be user-specified zone settings that can be recalledwith a single multicast command. In an embodiment, the data element 230may include other sensing device 75 information, such as areas orlocations of a building where the sensing devices 75 on the local areanetwork (e.g., 70 of FIG. 3) reside.

In an embodiment, the category of data element 240 that regards groupsof actuating devices 74 may include groupings of specific such devices,such as zone-based groups regarding zones in which the devices arelocated, smart groups such as groups based on device needs within azone, and/or user-specified groups. For example, groups of actuatingdevices 74 may be or include all actuating devices 74 that are, or whichcontrol, lights and outlets on a certain floor, all conference roomlights, and conference room outlets on a certain floor. In anembodiment, the data element 240 also includes groupings of sensingdevices 75.

In an embodiment regarding the backup system 1, the gateway 10 mayprocess data elements (210, 220, 230, and/or 240) of the data 200 tocontrol operation of the one or more actuating devices 74. The gateway10 may so control those devices by sending instructions through thelocal area network (e.g., 70 in FIG. 3) directly to the devices 74, orindirectly such as through nodes 72, to prompt those devices 74 tooperate in a certain way and/or at a certain time. For example, thegateway 10 may process the data element 210 regarding device informationto identify certain actuating devices 74, such as lights (or switchesfor lights). Thus, the gateway 10 may process data element 220 regardingscheduled events to determine that those lights may be turned off at 8PM every day. The gateway 10 may process data element 230 to determine azone of a building, such as a floor, in which those lights should beturned off. The gateway 10 may then, such as upon receiving a signalfrom its clock 38, send a message through the local area network (e.g.,70 in FIG. 3) to a node or nodes 72 (see FIG. 3) at 8 PM to cause theconnected actuating devices 74 that are lights (and/or are switches thatcontrol the lights) within the specified zone to be turned off. Inanother embodiment, the gateway 10 may process the data element 240regarding a group of actuating devices 74 that is all conference roomlights (and/or switches for those lights), such that the gateway 10 maysend a message to the node or nodes 72 to cause all those conferenceroom lights to be turned off, possibly at a certain time by processingthe data element 230 regarding scheduled events.

In other embodiments, there may be more or fewer categories of dataelements of the data 200 regarding the operation of the actuatingdevices 74 (and possibly sensing devices 75 in an embodiment) on thelocal area network (e.g. 70 in FIG. 3), and the data 200 may bedifferently distributed among those categories. Thus, there may be moreor fewer than data elements 210, 220, 230, and 240, such as by combiningor dividing those data elements.

In an embodiment of the data 200, in addition to data elements regardingthe operation of a plurality of actuating devices 74, the data 200 mayfurther regard other items. Thus, the data 200 may further include acategory of data element 250 regarding gateway 10 information. Thatinformation may include MAC address, information regarding any cloudwith which the gateway 10 directly or indirectly communicates and/or itscomponents, hostname, model, update schedule, enabled feature mask,security settings, network information such as a ZigBee® network thegateway 10 created, and/or other information regarding the gateway 10.That information may, for example, identify the gateway 10 and/or regardsettings of the gateway 10.

In an embodiment, the data 200 may further include a category of dataelement 260 regarding time settings. For example, the data element 260may regard local time settings and include the time zone and daylightsavings adjustment settings. In an embodiment, the gateway 10 mayprocess the data element 260 to change the time of the clock 38 based onthose settings.

In embodiments, and as described below, the backup system 1 and gateway10 may use signatures to efficiently backup and restore data, such asdata 200 including one or more of its categorized data elements (210,220, 230, 240, 250, and 260), stored on the gateway 10 (e.g., memory 20,a data storage device 36, a combination of both memory 20 and the datastorage device 36, or another device or devices for local storage ofdata on the local area network 70). If the data on the gateway 10 localstorage changes, such as by being updated or restored, the gateway 10may send a message through the local area network (e.g., 70 in FIG. 3)to change the operation of one or more actuating devices 74 (andpossibly also sensing devices 75 in an embodiment) on that network. Inan embodiment, the gateway 10 storage of the backup system 1 is orincludes a storage medium including code executable by the processor 12of the gateway 10 to cause the data 200 backup and restore and tooperate, or change the operation of the actuating devices 74, such asdescribed in the methods 300 and 500 of FIGS. 5 and 6, respectively.

FIG. 5 is a flow chart of a method 300 for backing up data on a gateway.In an embodiment, the gateway 10 such as described in embodiments hereinperforms such a backup method, though in other embodiments the method300 may be performed, at least in part with the gateway 10, by a generalpurpose computer 76 or another device or devices. The method 300 isdescribed herein as using the backup system 1 shown and described above,though in other embodiments the method 300 may use other configurationsof backup systems and gateways. At 310, the gateway 10 may store thereon(e.g., in or on memory 20, a data storage device 36, a combination ofboth memory 20 and the data storage device 36, or another device ordevices for local storage of data on the local area network (e.g., 70 ofFIG. 3)) data 200 comprising data elements that are each in a differentone of a plurality of categories that together regard the operation of aplurality of actuating devices 74 on the local area network (e.g., 70 inFIG. 3) on which the gateway 10 resides. The data elements may include,for example, the data element 210 in the category that includesactuating device information that, at least in part, identifies theactuating devices 74 on the local area network (e.g., 70 in FIG. 3), andthe data element 220 in the category includes scheduled events regardingthe identified devices 74. The data elements may also or alternativelyinclude the data element 230 that includes zones in which the actuatingdevices 74 are located and/or the data element 240 that regards groupsof actuating devices 74. As described above, in an embodiment thegateway 10 may also store in the data elements 210-240 similar sensingdevice 75 information and/or information associating the sensing devices75 with the actuating devices 75.

In an embodiment at 310, the gateway 10 of the backup system 1 mayfurther store data 200 comprising the data element 250 in the categoryregarding gateway information. In an embodiment at 310, the gateway 10of the backup system 1 may further store data 200 comprising the dataelement 260 in the category regarding time settings.

At 320, the data 200 may be stored on the database 100 as desired. Forexample, in an embodiment the gateway 10 may copy the data 200 stored onthe gateway 10 to the database 100. As described above, the database 100may be, in an embodiment, a remote database on a remote network 110 andon, or in communication with such as via the Internet, a remote server120. In that embodiment, the gateway 10 may copy the data 200 and itsdata elements (e.g., 210, 220, 230, 240, 250, and 260) to the database100 via the gateway 11 or otherwise to the database 100 such that thedatabase 100 stores that copy the gateway 10 transmitted thereto. Thedata 200 may be otherwise stored on the database 100 in otherembodiments.

At 330, the backup system 1 stores on the database 100 a signatureincluding sub-signatures that each represent a different one of the dataelements (e.g., 210, 220, 230, 240, 250, and 260) of the data 200 alongwith the corresponding data element category. The storing on thedatabase 100 of the signature may be as desired, such as by first havingthe gateway 10 or another device create the signature and transmit thatsignature or a copy thereof to the database 100 for storage, orotherwise as desired. In embodiments, any of the signatures describedherein (e.g., signature 400, updated signature, archived signatures,etc.) may be stored other than where described, such as all being storedon the gateway 10 and/or elsewhere on the local area network (e.g., 70of FIG. 3) or the network 110, for example.

Referring back to FIG. 4, the signature may be or include the signature400 comprising sub-signatures. Each sub-signature may itself be aseparate signature. The sub-signatures may each represent a differentone of the data elements of the data 200 along with the correspondingcategory to which that data element belongs. For example, in anembodiment, the signature 400 comprises sub-signature 410 thatrepresents the actuating device 74 information category of data element210, sub-signature 420 that represents the scheduled events regardingthe devices 74 category of data element 220, sub-signature 430 thatrepresents the category of data element 230 that includes zones in whichthe devices 74 are located, sub-signature 440 that represents thecategory of data element 240 that regards groups of devices 74,sub-signature 450 that represents the category of data element 250 thatregards gateway 10 information, and sub-signature 460 that representsthe category of data element 260 that regards time settings.

The backup system 1 may create the signature 400 as desired. Forexample, in an embodiment the signature 400 is created by the gateway 10and/or a general purpose computer 76 or other device by running eachdata element (e.g., 210, 220, 230, 240, 250, and 260) of the data 200through a function that converts that data element into a value that isthe sub-signature for that data element. The function may be or employ achecksum, cyclic redundancy check (CRC), hash, or other mathematicaloperation that converts a set of data into a sub-signature that isitself a finite signature. In an embodiment, the function may be onethat makes it unlikely that different data elements will produce thesame sub-signature. The sub-signatures for the data elements may then beconcatenated into the signature 400. In an embodiment, thesub-signatures are fixed lengths such that the sub-signatures may bereadily extracted from the signature 400. For example, thesub-signatures may be two units each, such as two letters or numbers.Those sub-signatures may be concatenated into an organized whole suchthat every two units of the signature 400 represent a known differentone of the data elements (e.g., 210, 220, 230, 240, 250, and 260) andits corresponding category.

Referring again to FIG. 5 and the backup method 300, at 340, the data200 stored on the gateway 10 may be updated by updating the dataelements of the data 200. The data elements may be so updated bychanging one or more of the data elements. For example, the dataelements may include data elements 210, 220, 230, 240, 250, and 260. Auser may update that data 200 and those data elements, which may resultin changing data elements 210 and 230 by replacing those data elements210 and 230 with different data, while not altering the categories ofdata elements 220, 240, 250, and 260. Those updated data elements inthat example are thus the data elements (210-260) that still correspondto the same categories, except the data elements 210 and 230 arechanged.

At 350, an updated signature is created. The updated signature may becreated in the same way the signature was created, as described above,with updated sub-signatures each representing a different updated dataelement and the category to which that different data element belongs.Thus, referring again to the example in which data elements 210 and 230of the data 200 were changed to result in the updated data and updateddata elements, the updated signature is changed to reflect changes tothose updated data elements. Thus, as data elements 210 and 230 wererepresented by sub-signatures 410 and 430, respectively, of thesignature 400, the updated signature and its updated sub-signatures arethe same as the signature 400 and sub-signatures 410-460 except theupdated sub-signatures corresponding to sub-signatures 410 and 430 arechanged. The updated signature with updated sub-signatures may be storedon the gateway 10 as described herein or otherwise stored where desired.

At 360, the backup method 300 may determine that the updated signaturedoes not match the signature 400, such as by having the gateway 10compare the updated signature and the signature 400 stored on thedatabase 100 to determine that they do not match.

At 370, after determining at 360 that the updated signature does notmatch the signature 400, the gateway 10 may determine, for each of theplurality of categories of data elements of the data 200 (and thus foreach same category of updated data elements of the updated data),whether the corresponding updated sub-signature of the updated signatureand sub-signature (e.g., 410, 420, 430, 440, 450, or 460) of thesignature 400 representing that category are different.

In an embodiment, at 380, because the data has been updated on thegateway 10 and is to be backed up on the database 100 as described belowat 390, the backup system 1 may archive the data 200 stored on thedatabase 100, such as by having the server 120 by prompt from thegateway 10, save another copy of the data 200 on the database 100 alongwith identifying information, such as meta-data including, as desired,creation date, last updated time such as a date including time, and/or aUniversally Unique Identifier (UUID). The backup system 1 may archivethe data 200 in association with the signature 400 such that the data200 and signature 400 are linked. Thus, if the data 200 is to berestored to the gateway as described below in the method 500 of FIG. 6,the backup system 1 may compare the archived signature 400 with thecurrent signature on the gateway 10 as described herein to efficientlydetermine changes to the data elements of the current data on thegateway 10 as compared to the data elements of the archived data 200.

At 390, for each updated sub-signature of the updated signature that isdifferent than the sub-signature (e.g., 410, 420, 430, 440, 450, or 460)in a corresponding category represented by that sub-signature andupdated sub-signature, the gateway 10 may copy to the database 100 theupdated data element represented by that updated sub-signature. In sotransmitting each such updated data element copy, the updated dataelement may replace the same category of the data element (e.g., 210,220, 230, 240, 250, and 260) of the data 200 stored on the database 100.

In an embodiment, at 390 the gateway 10 may further replace thesignature 400 on the database 100 with the updated signature. Forexample, the gateway 10 may transmit a copy of the entire updatedsignature to the database 100 to replace the entire signature 400 storedon the database 100. Alternatively, the gateway 10 may transmit forreplacement on the database 100 only a copy of the updatedsub-signatures that are different than the sub-signatures (e.g., 410,420, 430, 440, 450, and/or 460) of the signature 400 for eachrepresented category.

In an embodiment at 392, the backup system 1, via the updated data andupdated data elements stored on the gateway 10, may cause, by way of thegateway 10, a change in operation of one or more of the actuatingdevices 74 on the local area network (e.g., 70 of FIG. 3). For example,the updated data elements may include an updated version of the dataelement 220 regarding scheduled events, such as an update to the timingof operation of actuating devices 74 that are or actuate certain lightswithin the local area network (e.g., 70 in FIG. 3). The gateway 10 maythus transmit a signal, such as to those lights or to a node 72, such asa router or gateway, that controls those lights (or switch therefore),to change the timing of when those lights turn off at night. The updateddata elements may also or alternatively include an updated version ofthe data element 230 regarding zones in which the actuating devices 74are located. For example, that updated version may include a change inthe zone of lights that are to be turned off at the specified time, suchas changing the zone from conference room lights of a floor to alllights of the floor. As described above, if desired, the changing intiming of operation of the actuating devices 74 may be triggered byusing the clock 38 of the gateway 10 to signal to the gateway 10 thatthe revised time has been reached. In another example, the updated dataelements may change the condition sensed by a sensor device 75 thatwould trigger an event by an actuating device 74, such as a differenttemperature sensed by a sensor device 75 that would trigger an HVAC (orcontroller therefore) actuating device 74 to turn on air conditioning.In an embodiment in which data elements 210-240 include similarinformation regarding sensing devices 75 as with the actuating devices74, the gateway 10 may also transmit a signal to change the operation ofone or more sensing devices 75.

In an embodiment, the method 300 is repeatedly performed. Thus, forexample, after the method 300 has been completed, at least through 390,the current (non-archived) backed up data on the database 100, includingupdates to that data in the form of the gateway 10 data elements copiedto the database 100 as described above at 390, may again be the samedata that is on the gateway 10. Thus, the method 300 may be performedagain by the system 1 with the current (last-updated) data consideredbeing stored on both the gateway 10 at 310 and database 100 at 320, witha copy of the current (last-updated) signature and its sub-signaturescorresponding to that (last-updated) data stored on the database 100 at330 and possibly also stored on the gateway 10. Further, those current(last-updated) data elements of the (last-updated) data may again beupdated on the gateway 10 at 340 and a new signature with sub-signaturesmay be created at 350 for the newly-updated data and data elements onthe gateway 10. The method 300 can continue at 360 through 390, asdescribed in more detail above, by, e.g., comparing the new signaturewith the (last-updated) signature on the database 100 such that thenewly-updated data elements that changed may be determined and thencopied from the gateway 10 to the database 100, possibly after archivingthe current (last-updated) data and (last-updated) signature on thedatabase 100. Thus, the current data and data elements on the gateway 10and database 100 may again match. Further, the new signature stored orotherwise associated with the newly-updated data on the gateway 100 maybe copied to the database 100.

A user of the system 1 may desire to restore to the gateway 10 one ormore updated data elements of the updated data stored on the database100. For example, one or more categories of updated data elements of theupdated data stored on the gateway 10 may have changed again, such as bybeing corrupted. In such a case, the same one or more categories ofupdated data elements stored on the database 100 may be copied from thedatabase 100 to the gateway 10, and thereby replace the one or morefurther changed (e.g., corrupted) updated data elements on the gateway10. In an embodiment, that restoration may include first creating andcomparing a further updated signature and its further updatedsub-signatures on the gateway 10 associated with the further changeddata with the updated signature and its updated sub-signatures stored onthe database 100 to determine which corresponding data elements of thefurther updated data have changed. The restoration may be similar tothat described with respect to the method 500 for restoring data on agateway described below with respect to FIG. 6.

FIG. 6 is a flow chart of a method 500 for restoring data on a gateway.In an embodiment, the method 500 is part of a backup method includingthe method 300 of FIG. 5 described above. As with the method 300, in anembodiment the gateway 10 of the backup system 1 performs the method 500and the system 1 will be referred to when describing the method 500,though in other embodiments the method 500 may be performed, at least inpart with the gateway 10, by a general purpose computer 76 or anotherdevice or devices.

At 510, the database 100 may store a plurality of sets each of archiveddata and a corresponding archived signature. Each set of archived datamay include archived data elements in the categories of data elements(e.g., 210, 220, 230, 240, 250, and 260) of the data 200 describedabove. The archived data and archived data elements may be a copy ofdata that had been transmitted from the gateway 10. For example, eachtime the data (e.g., 200) on the gateway 10 is backed up to the database100 such as described above with respect to the method 300 of FIG. 5,the server 120 or another device may first back up the last backed updata (e.g., updated data and its updated data elements in method 300embodiment of FIG. 5) on the database 100. Thus, there may be many setsof archived data with corresponding archived data elements stored on thedatabase 100, and stored along with that archived data may be meta-dataincluding, for example, one or more identifiers such as the creationdate, last updated date, a Universally Unique Identifier (UUID), and/ora counter value that is incremented with each successive set of archiveddata and corresponding archived signature to indicate archived dataversion.

For each set of archived data, at 510 an associated archived signaturemay be stored on the database 100. The archived signature may includearchived sub-signatures that each represent a different one of thearchived data elements, and thus that each represent a different one ofthe plurality of categories, such as described above with respect to thesignature 400 and the sub-signatures (e.g., 410, 420, 430, 440, 450, and460). At least some of the plurality of categories may thus togetherregard the operation of the plurality of actuating devices 74 (andpossibly also sensing devices 75 in an embodiment) on the local areanetwork (e.g., 70 of FIG. 3). The archived signature and archivedsub-signature may have been created, such as described in the method 300of FIG. 5 at 330 and 350, to represent data and data elements (originalor updated one or more times) stored on the gateway 10 at least for atime.

Because each set of archived data and archived data elements stored at510 on the database 100 may be a backup of the gateway 10 data at adifferent time and possibly after a change to that data on the gateway10, each set of archived data may be different than the previous setsuch that one or more archived data elements of that set is changedrelative to the previous archived set of archived data elements. Thus,also, the associated archived signature in a set may be different thanthe archived signature in the previous set. Thus, as used herein, setsof archived data and their data elements, along with the associatedarchived signature, may all be different, or at least may be differentcompared to the previously backed up set, though successive sets ofarchived data and signatures may be the same in one or more cases inother embodiments.

At 520, one of the sets of archived data and corresponding archivedsignature may be selected. For example, one or more of the data elementsof the data currently stored on the gateway 10 may be corrupted, and auser may desire to restore a set of data and data elements that wasstored on the gateway 10 before that corruption. A user may otherwisedesire to restore data that had been stored on the gateway 10 and backedup to the database 100 on a prior date. The gateway 10, such as via auser communication therewith via a general purpose computer 76 or otherdevice, may select the set of archived data and corresponding archivedsignature such as based on, as described above, one or more identifierssuch as the creation date, last updated date, and/or a UniversallyUnique Identifier (UUID).

At 530, for the set of archived data and corresponding archivedsignature selected at 520, the system 1, such as via the gateway 10,determines that the archived signature stored on the database 100 doesnot match the updated signature stored on the gateway 10. The system 1may make this determination by having the gateway 10 compare the updatedsignature associated with the updated data (or otherwise currentsignature associated with the current data) stored on the gateway 10 andthe archived signature to determine that they do not match.

At 540, for each of categories represented by the updated sub-signaturesof the updated signature stored on the gateway 10 and correspondingarchived sub-signatures of the archived signature stored on the database100, the system 1 may determine whether that updated sub-signature andarchived sub-signature are different.

At 550, for each such archived sub-signature that is different from thecorresponding updated sub-signature for each represented category, thearchived data element represented by that archived sub-signature may becopied to the gateway 10, such as by the gateway 10 issuing a command toretrieve that archived data element. The command may be issued throughthe gateway 11 and/or server 120 in an embodiment. Each retrievedarchived data element may replace on the gateway 10 the correspondingupdated data element in the same category. Also at 550, in anembodiment, the archived signature may be copied to the gateway 10 toassociate with the current data and data elements on the gateway 10. Inthat embodiment, the current immediate backup data and correspondingsignature stored on the database 100 in the method 300 may also bechanged to match the current data and signature now on the gateway 10.That change may be effected by using signatures as described in themethod 300 if desired, or may use a similar method to copy over changeddata elements of the selected archived data on the database 100 to thelatest backup set of data (created in the method 300 above) on thedatabase 100. As described herein, the database 100 may be consideredone or more databases such that the copying of the changed data elementsfrom the archive to the latest backup (as described in the method 300)on the database 100 may be a copying between different databases ifdesired.

At 560, the gateway 10 may send a signal through the local area network(e.g., 70 in FIG. 3), such as through a node 72, such as a router orgateway, to change the operation of at least one of the devices 74 and75 based on the replacement of the updated data elements on the gateway10 with the archived data elements.

In an embodiment, a change to data (e.g. 200) by way of change to one ormore data elements (e.g. 210, 220, 230, 240, 250, and/or 260) asdescribed herein may occur by gateway 10 replacement or the addition orremoval of actuating devices 74 and/or sensing devices 75 reported tothat gateway 10. In an embodiment, gateway 10 replacement may berecognized by the system 1 when the gateway 10 has no data storedthereon and/or no associated data signature. In that embodiment, thesystem 1 may assume that the gateway 10 is a new or replacement deviceon the local area network (e.g., 70 of FIG. 3) and may restore all data(e.g., 200) last copied to the database 100, including all data elements(e.g., 210, 220, 230, 240, 250, and 260) by copying that data from thebackup database 100 to the gateway 10. In another embodiment, thegateway 10 may have a process for periodically backing up the datacurrently on the gateway 10.

As described in embodiments herein, the gateway backup system 1 andmethod 300 (and possibly also 500) embodiments herein may preservebandwidth by efficiently backing up and restoring on the gateway onlyspecific categories of elements of data regarding (possibly among otherthings) the operation of actuating devices (and possibly sensing devicesin an embodiment). By using signatures with sub-signatures thatrepresent those specific categories of data elements, the backup systemand method embodiments herein more efficiently determine whichcategories of data elements should be backed up or restored. Thus, thebackup system and method may more economically change the operation ofactuating devices (and possibly sensing devices in an embodiment) on alocal area network with which the gateway communicates.

While the disclosure has been described in detail and with reference tospecific embodiments thereof, it will be apparent to one skilled in theart that various changes and modifications can be made therein withoutdeparting from the spirit and scope of the embodiments. Thus, it isintended that the present disclosure cover the modifications andvariations of this disclosure provided they come within the scope of theappended claims and their equivalent.

What is claimed is:
 1. A backup method, comprising: storing, on a gateway on a local area network, data that comprises data elements that are each in a different one of a plurality of categories that together regard operation of a plurality of actuating devices on the local area network; storing the data on a database; creating a signature comprising sub-signatures that each represent a different one of the data elements along with the category that data element is in; updating the data stored on the gateway by updating the data elements, such that the updated data elements of the updated data comprise the data elements except that one or more of the data elements in one or more of the plurality of categories are changed; creating an updated signature that comprises updated sub-signatures that each represent a different one of the updated data elements of the updated data stored on the gateway, and thus each represent said different one of the plurality of categories; determining that the updated signature does not match the signature; determining, for each of the categories, whether the updated sub-signature and sub-signature representing that category are different; and copying, from the gateway to the database, for each category in which the updated sub-signature and sub-signature representing that category are different, the updated data element in that category and thereby replacing, with that updated data element, the data element in that category stored on the database.
 2. The method of claim 1, further comprising causing, by way of the gateway, via the updated data comprising the updated data elements stored on the gateway, a change in operation of one or more of the plurality of actuating devices.
 3. The method of claim 2, wherein the change in operation of the one or more of the plurality of actuating devices comprises a change in operation of at least one actuating device in a specified zone.
 4. The method of claim 2, wherein the change in operation of the one or more of the plurality of actuating devices comprises a change in operation of at least one actuating device based, at least in part, on a change to a set condition to be sensed by one or more sensing devices.
 5. The method of claim 1, further comprising, before the copying, from the gateway to the database for each category in which the updated sub-signature and sub-signature representing that category are different, of the updated data element in that category and thereby the replacing, with that updated data element, the data element in that category stored on the database: archiving the data and the signature.
 6. The method of claim 1, further comprising: further updating the updated data stored on the gateway by further updating the updated data elements, such that the further updated data elements of the further updated data comprise the updated data elements except that one or more of the updated data elements in one or more of the plurality of categories are changed; creating a further updated signature that comprises further updated sub-signatures that each represent a different one of the further updated data elements of the further updated data stored on the gateway, and thus each represent said different one of the plurality of categories; determining that the further updated signature does not match the updated signature; determining, for each of the categories, whether the updated sub-signature and the further updated sub-signature representing that category are different; copying, from the database to the gateway, for each category in which the updated sub-signature and further updated sub-signature representing that category are different, the one of the data element and the updated data element in that category stored on the database and thereby replacing, with that copied one of the data element and the updated data element, the further updated data element in that category stored on the gateway.
 7. The method of claim 1, further comprising: storing, on the database, a plurality of sets each comprising both archived data and a corresponding archived signature, wherein for each of the sets: the storing of the archived data comprises storing archived data elements that are each in a different one of the plurality of categories regarding the operation of the plurality of actuating devices on the local area network; and the storing of the archived signature comprises storing archived sub-signatures that each represent a different one of the archived data elements of the archived data, and thus each represent one of the different ones of the plurality of categories; selecting one of the sets comprising both the archived data and the corresponding archived signature; determining, for the selected set of both the archived data and the corresponding archived signature, that the archived signature does not match the updated signature; determining for the selected set of both the archived data and the corresponding archived signature, for each of the categories, whether the archived sub-signature and updated sub-signature representing that category are different; and copying, from the selected set of both the archived data and the corresponding archived signature, from the database to the gateway, for each category in which the archived sub-signature and updated sub-signature representing that category are different, the archived data element in that category and thereby replacing, with that archived data element, the updated data element in that category stored on the gateway.
 8. The method of claim 7, further comprising changing, by way of the gateway, the operation of at least one of the actuating devices by way of the replacement of the updated data element stored on the gateway with the archived data element for said each category in which the archived sub-signature and updated sub-signature representing that category are different.
 9. A backup system, comprising: a gateway on a local area network, the gateway comprising a processor and a computer readable storage medium, the computer readable storage medium including code executable by the processor to: store, on a gateway on a local area network, data that comprises data elements that are each in a different one of a plurality of categories that together regard operation of a plurality of actuating devices on the local area network; store the data on a database; create a signature comprising sub-signatures that each represent a different one of the data elements along with the category that data element is in; update the data stored on the gateway by updating the data elements, such that the updated data elements of the updated data comprise the data elements except that one or more of the data elements in one or more of the plurality of categories are changed; create an updated signature that comprises updated sub-signatures that each represent a different one of the updated data elements of the updated data stored on the gateway, and thus each represent said different one of the plurality of categories; determine that the updated signature does not match the signature; determine, for each of the categories, whether the updated sub-signature and sub-signature representing that category are different; and copy, from the gateway to the database, for each category in which the updated sub-signature and sub-signature representing that category are different, the updated data element in that category and thereby replace, with that updated data element, the data element in that category stored on the database.
 10. The system of claim 9, the computer readable storage medium including code executable by the processor of the gateway to further: cause, by way of the gateway, via the updated data comprising the updated data elements, a change in operation of one or more of the plurality of actuating devices.
 11. The system of claim 10, wherein the change in operation of the one or more of the plurality of actuating devices comprises a change in operation of at least one actuating device in a specified zone.
 12. The system of claim 10, wherein the change in operation of the one or more of the plurality of actuating devices is based, at least in part, on a change to a set condition, sensed by one or more sensing devices, that triggers the change in operation.
 13. The system of claim 10, the gateway further comprising a clock, the change in operation of the one or more of the actuating devices comprising using the clock on the gateway to signal to the gateway to cause a change in a timing of operation of at least one of the one or more of the actuating devices.
 14. The system of claim 9, wherein the plurality of categories together further regard operation of a plurality of sensing devices on the local area network.
 15. The system of claim 14, the computer readable storage medium including code executable by the processor of the gateway to further: cause, by way of the gateway, via the updated data comprising the updated data elements, a change in operation of one or more of the plurality of sensing devices.
 16. The system of claim 9, the plurality of categories regarding the operation of the plurality of actuating devices on the local area network comprising one or more categories that together identify the actuating devices and another category that comprises scheduled events regarding the identified actuating devices.
 17. The system of claim 9, the data further comprising an additional data element that is in an additional category comprising gateway information.
 18. The system of claim 9, the data further comprising an additional data element that is in an additional category regarding time settings.
 19. The system of claim 9, the computer readable storage medium including code executable by the processor of the gateway to further: further update the updated data stored on the gateway by further updating the updated data elements, such that the further updated data elements of the further updated data comprise the updated data elements except that one or more of the updated data elements in one or more of the plurality of categories are changed; create a further updated signature that comprises further updated sub-signatures that each represent a different one of the further updated data elements of the further updated data stored on the gateway, and thus each represent said different one of the plurality of categories; determine that the further updated signature does not match the updated signature; determine, for each of the categories, whether the updated sub-signature copied to the database and the further updated sub-signature representing that category are different; copy, from the database to the gateway, for each category in which the updated sub-signature and further updated sub-signature representing that category are different, the one of the data element and the updated data element in that category stored on the database and thereby replace, with that copied one of the data element and the updated data element, the further updated data element in that category stored on the gateway.
 20. The system of claim 9, wherein the database is on a network that is remote from the local area network.
 21. The system of claim 9, the computer readable storage medium including code executable by the processor of the gateway further to: store, on the database, a plurality of sets each comprising both archived data and a corresponding archived signature, wherein for each of the sets: the storing of the archived data comprises storing archived data elements that are each in a different one of the plurality of categories regarding the operation of the plurality of actuating devices on the local area network; and the storing of the archived signature comprises storing archived sub-signatures that each represent a different one of the archived data elements of the archived data, and thus each represent one of the different ones of the plurality of categories; select one of the sets comprising both the archived data and the corresponding archived signature; determine, for the selected set of both the archived data and the corresponding archived signature, that the archived signature does not match the updated signature; determine for the selected set of both the archived data and the corresponding archived signature, for each of the categories, whether the archived sub-signature and updated sub-signature representing that category are different; and copy, from the selected set of both the archived data and the corresponding archived signature, from the database to the gateway, for each category in which the archived sub-signature and updated sub-signature representing that category are different, the archived data element in that category and thereby replace, with that archived data element, the updated data element in that category stored on the gateway of the local area network.
 22. The system of claim 21, the computer readable storage medium including code executable by the processor of the gateway to further change, by way of the gateway, the operation of at least one of the actuating devices by way of the replacement of the updated data element stored on the gateway with the archived data element for said each category in which the archived sub-signature and updated sub-signature representing that category are different.
 23. A data backup system, comprising: a remote database that is remote from a local area network, the remote database storing: first data that comprises first data elements that are each in a different one of a plurality of categories regarding operation of a plurality of actuating devices on the local area network; and a first signature comprising first sub-signatures that each represent a different one of the data elements along with the corresponding said different one of the plurality of categories that data element is in; a gateway on the local area network, the gateway storing: second data that comprises second data elements that each are in a different one of the plurality of categories regarding the operation of the plurality of actuating devices on the local area network; and a second signature that comprises second sub-signatures that each represent a different one of the second data elements of the second data, and thus each represent said different one of the plurality of categories that second data element is in; wherein the gateway comprises a processor and a computer readable storage medium including code executable by the processor to: determine whether the second signature matches the first signature, and if the second signature does not match the first signature, determine, for each of the plurality of categories, whether the corresponding second sub-signature and first sub-signature representing that category are different; and copy, from the gateway to the remote database, for each category in which the second sub-signature and first sub-signature representing that category are different, the second data element in that category and thereby replacing, with that second data element, the first data element in that category stored on the remote database.
 24. A data backup system, comprising: a remote database that is remote from a local area network, the remote database storing a plurality of sets each of both first data and a corresponding first signature, wherein the first data is different in at least a plurality of the sets and the first signature is different in at least a plurality of the sets, wherein for each of the sets: the first data comprises first data elements that each represent a different one of a plurality of categories regarding operation of a plurality of actuating devices on the local area network; and the first signature comprises first sub-signatures that each represent both a different one of the first data elements of the first data and the category that different one of the first data elements is in; a gateway on the local area network, the gateway storing: second data that comprises second data elements that each are in said different one of the plurality of categories regarding the operation of the plurality of actuating devices on the local area network; and a second signature that comprises second sub-signatures that each represent a different one of the second data elements of the second data, and thus each represent said different one of the plurality of categories that second data element is in; wherein the gateway comprises a processor and a computer readable storage medium including code executable by the processor to: determine, for a selected one of the sets of both first data and corresponding first signature, whether the first signature matches the second signature, and if the first signature does not match the second signature, determine, for each of the plurality of categories, whether the first sub-signature and second sub-signature representing that category are different; and copy from the remote database to the gateway, for the selected one of the sets of first data and corresponding first signature, for each first sub-signature that is different than the corresponding second sub-signature for each of the represented plurality of categories, the first data element in that category and thereby replace, with that first data element, the second data element in that category stored on the gateway.
 25. The data backup system of claim 24, the gateway comprising the processor and the computer readable storage medium including code executable by the processor to further, via said for each first sub-signature that is different than the corresponding second sub-signature for each of the represented plurality of categories, said replacing, with that first data element, the second data element in that category stored on the gateway: cause a change in operation of at least one of the plurality of actuating devices on the local area network. 